-
Notifications
You must be signed in to change notification settings - Fork 919
Retry Markdown link checks on HTTP 429 (v1) #2186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry Markdown link checks on HTTP 429 (v1) #2186
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds retry functionality to the markdown link checker to handle HTTP 429 (Too Many Requests) responses, specifically addressing failures with the http://reneefrench.blogspot.com/ site that frequently returns this status code during pre-commit checks.
- Added the
-rargument to enable automatic retrying on HTTP 429 responses - Included explanatory comment documenting the purpose of the retry flag
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
API Change ReportNo changes found! |
* release/1.17: Retry Markdown link checks on HTTP 429 (v1) (#2186)
* release/1.17: GODRIVER-3612 Add an internal-only NewSessionWithLSID API (v1) (#2183) Consider HTTP 429 a succcessful response in the Markdown link check. (#2191) Pin drivers-evergreen-tools to rev 98f6b0e in v1. (#2184) Retry Markdown link checks on HTTP 429 (v1) (#2186)
Summary
Retry Markdown link checks when the endpoint responds with HTTP 429.
Background & Motivation
The http://reneefrench.blogspot.com/ site returns HTTP 429 frequently, leading to failed pre-commit checks when run in the Github Actions runners. The markdown-link-check tool supports retrying after an HTTP 429, automatically waiting until the time specified by the "retry-after" HTTP header. See the usage docs for details.
See previous PR #2181